Centralizing sequence number generation

Many Meridian Enterprise customers use sequence numbers for document names and other properties. By default, sequence numbers are unique only within the current vault. Therefore, documents that use sequence numbers cannot be guaranteed to be unique among vaults that collaborate on the documents with the Global Collaboration Framework.

The Meridian Enterprise API and VBScript implementation support making calls to VBScript functions in remote vaults with the CallRemote function. The GCF uses this function, for example, to request ownership and to retrieve the status of a document in the collaborating vaults.

The following topics describe how to centralize sequence number generation at a central vault, for example, at the GCF hub site. This results in unique sequence numbers among all collaborating vaults.

For the purpose of the example, the numbering scheme is kept very simple: documents of the type Generic Document are named GEN-nnnnn and documents of other document types are named OTH-mmmmm. This example shows how information about new documents can be passed to the hub vault that generates the sequence numbers.